✓
Purchase Confirmed — Thank You

Your Pocket Guide is ready to download.

Your PDF is available below. We've also sent the download link to your email address.

PG-AIMS-LG-001 v1.0
ISO 42001 Clause 6.6 × SRA Code 6.3
Legal Edition
Check Stripe receipt for order ref
unuslondon.com

AI Vendor Due Diligence for Law Firms

Click the button below to download your pocket guide. If you experience any issues, email support@unuslondon.com and we'll resend the link within one business day.

Bookmark this page.  To re-download any time within 30 days, re-enter your email above. If you lose access, email support@unuslondon.com with your order reference and the relevant product code in the subject line.
Getting Started

How to Use This Guide — Week One Actions

01
Read Part 1 first — establish which SRA obligation is highest priority for your firm

Before moving to the implementation sequence, read the four SRA obligations in Part 1 and identify which one your firm is most exposed on right now. For most firms, Code 6.3 (confidentiality) is the starting point — it directly governs every AI system that processes client data. If your firm has any AI tool processing client instructions, documents, or matter information without a reviewed DPA, Code 6.3 exposure is open today.

02
Complete the Week 1 AI system inventory before anything else

The guide's Week 1 task — inventorying every AI tool in use at the firm — is the foundation everything else depends on. Do not skip to the six-question framework or the DPA checklist until you have a complete list. Include general-purpose tools that fee earners may be using individually (chatbots, drafting assistants, research tools) as well as firm-licensed platforms. An incomplete inventory produces an incomplete due diligence programme.

03
Assign the Tier 1 systems their risk designation before contacting vendors

Once your inventory is complete, use the three-tier model in Part 3 to assign each system a risk tier. Complete all tier assignments before sending the six-question framework to any vendor. This ensures your due diligence effort is correctly prioritised — Tier 1 systems (privileged client data, client-facing outputs) get full due diligence first, and Tier 3 systems (no client data) are handled last. The most common error is starting with the easiest vendor conversation rather than the highest-risk system.

04
Send the six questions to Tier 1 vendors in writing — not in a call

The six-question framework in Part 3 must be submitted in writing — email is sufficient — so that vendor responses are documented evidence. A verbal assurance from a sales team member that "we don't use your data to train our models" is not evidence. A written response that can be attached to the Vendor Due Diligence Record is. Send the questions by email, request written responses, and document the date of the response in the record.

05
Have the COLP review Tier 1 DPAs against the Part 2 contractual checklist — not the Practice Manager

DPA review for Tier 1 systems (privileged client data) requires the COLP or a nominated solicitor — not the Practice Manager acting alone. The DPA review is the point where the firm's legal judgement is applied to the vendor's contractual terms. The Part 2 contractual checklist gives the COLP a structured review framework rather than a blank-page exercise. Once reviewed, the COLP completes Section 5 (Risk Decision) of the Vendor Due Diligence Record and signs off.

06
Diarise annual review dates in the Unified Compliance Calendar before completing the programme

Vendor due diligence is not a one-time activity. Clause 6.6 requires ongoing monitoring and review. The final step of the seven-week sequence — diarising annual review dates — is the step that converts a one-time due diligence exercise into a sustained governance programme. Use the Unified Compliance Calendar (CAL-AIMS-LG-001) if you have it. If not, create calendar entries now: one annual review per Tier 1 and Tier 2 vendor, plus triggered review entries for vendor ownership changes, model updates, and security incidents.

Quick Reference

Six Questions & Evidence Required

The full framework is in your downloaded guide. This reference confirms the six questions and what each answer must produce.

PG-AIMS-LG-001 v1.0 · Six-Question Vendor Framework · Summary Reference

What to Ask. What to Demand in Writing.

#
Question
Evidence Required
Q1
Where is our data stored?
Written confirmation of data jurisdiction — UK, EU, or with UK GDPR-adequate safeguards
Q2
Do you use our data to train your models?
Written confirmation: no training use without opt-in consent — must appear in DPA, not just standard terms
Q3
Who are your sub-processors?
Current sub-processor list; advance notification of additions; DPA binds sub-processors to same standard
Q4
What is your incident notification commitment?
Contractual SLA: 24h best practice, 72h minimum (UK GDPR standard) — must be in the DPA
Q5
What are the known limitations of your AI system?
Written model card or limitations summary: hallucination rates, legal content handling, training data cutoff
Q6
How do we get our data back or deleted at end of contract?
DPA clause specifying deletion/return timeline, confirmation method, and data format for return

Summary only. Full question guidance, non-compliant answer identification, and response protocols are in Part 3 of your downloaded guide.

Vendor Due Diligence Record — Five Sections at a Glance

One record per vendor. Maintained in the firm's document management system. Cross-referenced in the AI register.

PG-AIMS-LG-001 v1.0 · Vendor Due Diligence Record Structure

Five Sections. ISO 42001 Clause 6.6 × SRA Code 6.3.

#
Section
Updated
S1
Vendor Identity
Legal name, jurisdiction, parent company, AI system name and version, contract reference, account manager
On change
S2
Pre-Adoption Assessment
Date, assessor, risk tier, six-question responses, security certification details and expiry, DPA reference
At adoption; on re-assessment
S3
Contractual Protections
DPA status, date reviewed, data jurisdiction, sub-processor list, incident SLA, training restriction, audit rights, exit clause
On contract change
S4
Ongoing Review Log
Date of last review, reviewer, changes noted, action taken, next review date
Annual minimum; triggered review
S5
Risk Decision
Overall risk rating, residual risk after controls, COLP sign-off name and date, any conditions on use
At adoption; at each review

Full record structure, evidence checklist, and gap-response table are in Part 4 of your downloaded guide.

ISO 42001 × SRA Standards & Regulations — Legal Series

Vendor Due Diligence Is Gap 9. Eight Gaps Remain.

This guide closes ISO 42001 Gap 9 against SRA Code 6.3. The complete dual-framework programme — all nine gaps closed across both frameworks — is the Integration Guide: Professional Conduct Meets AI Governance. Eight intersection chapters. Evidence consolidation method. 27-activity A2 Unified Compliance Calendar. For COLPs and Managing Partners implementing the full programme.

Free ✓ 5 Gaps That Create SRA Risk — available at unuslondon.com/legal-sra-ai-gaps
£19 Gap Severity Matrix — all 9 gaps · SRA mapping · severity ratings · EU AI Act
£47 ✓ AI Vendor Due Diligence Pocket Guide — you have this
£167 Integration Guide + Unified Compliance Calendar — Complete ISO 42001 × SRA dual-framework mapping across 8 intersection chapters. Evidence consolidation method with 11-step implementation sequence. 27-activity A2 Unified Compliance Calendar cross-referencing ISO 42001 and SRA obligations by month. For COLPs and Managing Partners closing all nine gaps.
Get the Integration Guide + Calendar — £167 → Or explore the full series at the Governance Academy — £97/month · 7-day free trial
Support

Questions or Access Issues?

Using the Guide

Questions about the framework or implementation

For questions about applying the six-question framework, interpreting vendor responses, or using the Vendor Due Diligence Record in a specific firm context, post in the Governance Academy community.

Governance Academy Community →
Download Access

Can't download or lost the link?

Email your Stripe order reference to our support address with "PG-AIMS-LG-001 resend" in the subject line. We resend access within one business day.

support@unuslondon.com →

Refund requests are handled through Stripe's 60-day guarantee — contact support@unuslondon.com with your order reference.